@rafmudaf , 3.8 is the only failing test, but 3.8 is also end of life:
https://devguide.python.org/versions/
Should I just remove it?

Changing the minimum Python version is kind of a big decision, so I wouldn't make that change just because a test is failing. However, whether to support Python 3.8 is a fair question. It may be worth asking for some community input.

In this case, the error is because you specified Python >= 3.9, but the GitHub Actions job is testing Python 3.8. So the fix as it relates to the scope of this pull request is to use requires-python = ">=3.8".

In this case, the error is because you specified Python >= 3.9, but the GitHub Actions job is testing Python 3.8. So the fix as it relates to the scope of this pull request is to use requires-python = ">=3.8".

You're right, think I've fixed this now

Regarding python versions, just wanted to remind of this #953 (originally in #950 and discussed a bit more in #951)

It appears that FLORIS isn't actually currently compatible with python 3.8 and 3.9 on Windows

Nice catch @misi9170, I think I understand @rafmudaf 's point to be that raising the python requirement for FLORIS is a valid discussion but should not be done within the context of this PR as it's out of scope

Nice catch @misi9170, I think I understand @rafmudaf 's point to be that raising the python requirement for FLORIS is a valid discussion but should not be done within the context of this PR as it's out of scope

Sounds good, agreed.

@paulf81 I was able to pip install this into a new conda environment and ran an example without issue.